ECK: Document recovery from failed volume upsize #3694
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Michael Montgomery <[email protected]>
Signed-off-by: Michael Montgomery <[email protected]>
Co-authored-by: Copilot <[email protected]>
Signed-off-by: Michael Montgomery <[email protected]>
Signed-off-by: Michael Montgomery <[email protected]>
Co-authored-by: Peter Brachwitz <[email protected]>
🔍 Preview links for changed docs |
pebrc
approved these changes
Oct 28, 2025
Signed-off-by: Michael Montgomery <[email protected]>
|
@kilfoyle I pinged you directly for this review as you reviewed the previous PR that I was forced to close. |
kilfoyle
reviewed
Oct 29, 2025
kilfoyle
approved these changes
Oct 29, 2025
Co-authored-by: David Kilfoyle <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I had to close #3459 due to my git failures...
In elastic/cloud-on-k8s#4467 it's noted that some users are dealing with volume expansion failure issues, and documenting how to recover from this situation would be helpful. This is the attempt to update that documentation.
After merge